upgrade rust to 1.85.0#11295
Conversation
f1ac25a to
c7fb2c2
Compare
mfrw
left a comment
There was a problem hiding this comment.
Can we please skip the failing tests, so that the pipeline is green.
Let's add a link where we skip to the FreeBSD forum to clarify on why are we even skiping :)
|
|
||
| %prep | ||
| %setup -q | ||
| %patch 2 -p1 |
There was a problem hiding this comment.
Potential for optimization but fine with me
There was a problem hiding this comment.
Is there a good reason for continuing to use %setup and %patch here instead of changing to %autosetup?
There was a problem hiding this comment.
Updated it to %autosetup
There was a problem hiding this comment.
I notice that you switched back away from %autosetup.
I don't mind this, because it keeps us closer to the OpenSUSE upstream, but I wanted to make sure that's intentional.
d372d75 to
46c915c
Compare
SPECS/rust/rust.spec
Outdated
| Patch1: CVE-2024-32884.patch | ||
| Patch2: CVE-2024-31852.patch | ||
|
|
||
| Patch0: Remove_cannot_write_error_test.patch |
There was a problem hiding this comment.
Patch0, 1: Re-verify if these fail in the pipeline. Both seem to have a similar issue (expect permission issues are revoking permissions with chmod, but the expected-to-fail commands still work)
There was a problem hiding this comment.
If tests fail, let's make a judgement on who and decide whether we want to fix resp. need to make some changes, or whether we'd want to accept this
There was a problem hiding this comment.
Test passed when run as non-root user
SPECS/rust/rust.spec
Outdated
|
|
||
| Patch0: Remove_cannot_write_error_test.patch | ||
| Patch1: Remove_leave_log_after_failure_test.patch | ||
| Patch2: Ignore_failing_ci_tests.patch |
There was a problem hiding this comment.
Let's specify which CI tests fail and re-assess
SPECS/rust/rust.spec
Outdated
| Patch1: Remove_leave_log_after_failure_test.patch | ||
| Patch2: Ignore_failing_ci_tests.patch | ||
| Patch3: skip-failing-run-make-tests.patch | ||
| Patch4: Ignore-test-for-aarch64.patch |
There was a problem hiding this comment.
error: linker aarch64-linux-gnu-gcc not found. Let's assess whether this is expected to fail for Azure Linux or e.g. whether the linker binary would need to be renamed.
Side note: Let's add some documentation for all the patch files we add. This way it becomes clear why we did this
SPECS/rust/rust.spec
Outdated
| Patch0: Remove_cannot_write_error_test.patch | ||
| Patch1: Remove_leave_log_after_failure_test.patch | ||
| Patch2: Ignore_failing_ci_tests.patch | ||
| Patch3: skip-failing-run-make-tests.patch |
There was a problem hiding this comment.
Let's document which of these are failing (three tests are failing) and re-assess.
There was a problem hiding this comment.
run-make tests passed when run as non-root user
Camelron
left a comment
There was a problem hiding this comment.
In retrospect, we should get to the bottom of why these patches removing tests are required before proceeding.
648a89f to
46c915c
Compare
ca87822 to
f17dae5
Compare
d486f8c to
74eaf3f
Compare
SPECS/flux/flux.spec
Outdated
| # Fixed upstream in 1.195.0, https://github.com/influxdata/flux/pull/5484. | ||
| Patch2: fix-build-warnings.patch | ||
| Patch3: fix-unsigned-char.patch | ||
| Patch4: 0001-Fix-with-latest-rust.patch |
There was a problem hiding this comment.
nit: Please fix spacing.
|
|
||
| %prep | ||
| %setup -q | ||
| %patch 2 -p1 |
There was a problem hiding this comment.
I notice that you switched back away from %autosetup.
I don't mind this, because it keeps us closer to the OpenSUSE upstream, but I wanted to make sure that's intentional.
| tar -xf %{SOURCE1} | ||
| install -D %{SOURCE2} .cargo/config | ||
|
|
||
| patch -p2 < %{PATCH1} |
There was a problem hiding this comment.
Looks like we're no longer applying PATCH1.
There was a problem hiding this comment.
Removed it mistakenly, adding it again
SPECS/flux/flux.spec
Outdated
| } | ||
| EOF | ||
|
|
||
|
|
There was a problem hiding this comment.
nit: remove extra blank line.
05eb833 to
43ca753
Compare
43ca753 to
6277f76
Compare
3e83972 to
c1b4f6d
Compare
9fe9ef3 to
3a96e33
Compare
| %define release_date 2023-11-16 | ||
| %define stage0_version 1.74.0 | ||
| %define release_date 2025-01-09 | ||
| %define stage0_version 1.84.0 |
There was a problem hiding this comment.
Is the 1.74.0 version capable of building the 1.85 version?
There was a problem hiding this comment.
Is the 1.74.0 version capable of building the 1.85 version?
No, it should be build with 1.84
Co-authored-by: kavyasree <kkaitepalli@microsoft.com>
Co-authored-by: kavyasree <kkaitepalli@microsoft.com>
Co-authored-by: kavyasree <kkaitepalli@microsoft.com>
Co-authored-by: kavyasree <kkaitepalli@microsoft.com>
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
What does the PR accomplish, why was it needed?
Change Log
Does this affect the toolchain?
NO
Associated issues
Links to CVEs
Test Methodology